1. Terms and definitions

For the purposes of this document, the terms and definitions given in CC/R 0610 and the following apply.

Clause 1.1Calendar

A collection of events, tasks, journal entries, etc. A calendar could be the content of a person or resource’s agenda; it could also be a collection of data serving a more specialized need. Calendars are the basic storage containers for calendaring information.

[SOURCE: IETF RFC 3283]
Clause 1.2Calendar User

An entity (often a human) that accesses calendar information.

[SOURCE: IETF RFC 3283]
Clause 1.3Calendaring

An application domain that covers systems that allow the interchange, access and management of calendar data.

Clause 1.4CalConnect

The Calendaring and Scheduling Consortium consisting of vendors and user groups interested in promoting and improving calendaring and scheduling standards and interoperability.

Clause 1.5Component

A piece of calendar data such as an event, a task, or an alarm. Information about components is stored as properties of those components.

[SOURCE: IETF RFC 3283]
Clause 1.6Event

A calendar object that usually takes up time on an individual calendar. Events are commonly used to represent meetings, appointments, anniversaries, and day events.

Clause 1.7Free time search

(Bounded) common free time. This is typically a search generated by an application to show time on a calendar that is available or open.

Clause 1.8Freebusy

A database and/or listing of times when a potential attendee or resource is free or busy. Used when scheduling calendar events.

Clause 1.9iCalendar

The Internet Calendaring and Scheduling Core Object Specification. An IETF standard (RFC 2445) for a text representation of calendar data (VEVENT, VTODO, VALARM, etc.).

Clause 1.10Instance

When used with recurrences, an instance refers to an item in the set of recurring items.

Clause 1.11Invite

To request the attendance of someone to a calendar event.

Clause 1.12Negotiation

Resource conflict resolution. Negotiation is the process of resolving conflicts either programmatically or via direct communication with the participants and invitees of meetings and events.

Clause 1.13Notification
  1. The action of making known, an intimation, a notice.

  2. Reminder or alarm sent when any resource or parties interested in the resource need an indicator that some attention is required. Possible notification methods include email, paging, audible signal at the computer, visual indicator at the computer, voice mail, telephone.

Clause 1.14Organizer

The originator of a calendar event typically involving more than one attendee.

Clause 1.15Property

A description of some element of an component, such as a start time, title, or location. Properties can have parameters associated with them to modify or add to their meaning.

Clause 1.16Publish

Make known publicly calendar information such as freebusy times.

Clause 1.17Reminders

See .

Clause 1.18Task

A calendar object that is commonly used to represent work items.

Clause 1.19Text/calendar

The MIME content type for encoding iCalendar objects. Example usage includes: email, web pages.